home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group98a.txt
/
000100_icon-group-sender _Thu Mar 5 08:21:31 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
3KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.8.7/8.8.7) with SMTP id IAA29054
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Thu, 5 Mar 1998 08:21:31 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA07338; Thu, 5 Mar 1998 08:21:30 -0700
Message-Id: <34FEC116.4952@gte.net>
Date: Thu, 05 Mar 1998 09:13:26 -0600
From: Mark Evans <evans@gte.net>
Reply-To: evans@gte.net
Organization: None
X-Mailer: Mozilla 3.01 (Win95; I)
Mime-Version: 1.0
To: icon-group@optima.CS.Arizona.EDU
Subject: Re: Icon to C conversion: C++ instead
References: <Pine.A32.3.91.980304210200.30650A-100000@pluto.mscc.huji.ac.il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 1541
Ehud Lamm wrote:
>
> The question really isn't wether C strings can be used as Icon strings,
> but rather that in order to produce good C code to function exactly like
> the Icon code (as compiled Icon should), you have first to deeply explore
> the bset ways to do the desired things in C. You shouldn't only think
> about compilation techniques and optimizations.
>
> Ehud Lamm mslamm@pluto.mscc.huji.ac.il
Agreed. We've been talking about C; a point probably missed in these
talks is that C++ could be the optimum route.
An (Icon)-->(C++) converter could base its conversion on a true class
library, not just a mere function library. CString might be one of
them, CStream another. My point is that there already exist large class
libraries in C++ and many of them are free on the web. So rather than
doing a lot of design, one could in principle just go shopping.
Type information for the classes should be available at runtime and at
compile time. That is the case with Microsoft VC++ 5.0 anyway. That
fact might resolve some of the typing issues in Icon. I agree with the
idea that typing should be available in Icon as an option, per Paul
Abrahams. It is a compiler optimization hint, essentially.
All of the C++ compilers that I know about nowadays are native C++
compilers; that is, they don't use the old CFront method of
preprocessing C++ code into mangled-C code and then compiling the
mangled-C with a C compiler. So they are quite efficient and elegant.
They compile C++ directly into machine code.
Mark